Add archive section #293
Add archive section #293
Conversation
|
|
||
| The long-term transition we hoped for has succeeded: in 2024 it is entirely | ||
| normal for projects to support only Python 3, simplifying maintainers' lives | ||
| and letting us take full advantage of newer language features. |
There was a problem hiding this comment.
I would add a phrase along the lines of "without disrupting users still using Python 2 at the time" maybe ?
Thanks for writing this !
There was a problem hiding this comment.
I've sort of mentioned this idea in the previous paragraph:
We didn't force people to move to Python 3, but if they wanted to stick with Python 2, they would stop getting new versions of our projects.
I don't want to over-sell this, because a) we wanted people in general to move to Python 3, even if Python 2 remained in some specific niches, to re-unify the Python world, and b) I'm sure the end of Python 2 support did disrupt people who needed/wanted to keep using it. Not our statement directly, but things like the removal of Python 2 from Linux distros, and the security concerns for anything that handles untrusted data. The python_requires stuff definitely helped to make things less painful, but it was never going to be totally disruption free.
|
After some fiddling, I've suceeded in getting this to build in a container:
The great big gap at the bottom of the section is a bit ugly - I guess it's space for the optional icon between sections, which we don't have here - but I'd say it's good enough. |
|
Let's give this a few more days for any comments and merge. Thanks ! |
+1, ok let's get that in. Thanks again. |
See discussion on #292.
@mscuthbert has a good idea about adding it to the README as well, but I figured we should get the wording right in one place first.